|
In the section "Configuring Static
Routes", static routes were configured on Hoboken to make networks
172.16.1.0 on Sterling and 172.16.5.0 on Waycross accessible
. Using
this configuration, nodes on Sterling’s 172.16.1.0 network cannot
reach nodes on the 172.16.5.0 network. From privileged EXEC mode on the
Sterling router, execute a
ping
to a node on the 172.16.5.0 network. The
ping
fails.
Now run a traceroute
from Sterling to the same address used in the previous ping statement.
Note where the traceroute
fails. The traceroute
indicates that the ICMP packet was returned from Hoboken but not from
Waycross.
This implies that the trouble exists either on Hoboken or Waycross.
Telnet to the Hoboken router. Try again to
ping
the node on the 172.16.5.0 network connected to the Waycross router.
This
ping
should succeed because Hoboken is directly connected to Waycross.

| |
Lab Activity
Lab Exercise: Configuring Static Routes
In this lab, the students will
configure static routes between routers to allow data transfer
between routers without the use of dynamic routing protocols.
|
|
|
| |
Lab Activity
e-Lab Activity: Static Routes
In this lab, the students will configure static routes
between routers to allow data transfer between routers without
the use of dynamic routing protocols.
|
|
|